8 articles tagged with ""concurrency""
Coming from 7 years of Laravel and Node.js, my mental model for shared state was simple: global variable, session, or Redis. Then Rust handed me Arc<Mutex<T>> and I had to unlearn everything. Turns out, when the compiler forces you to be honest about shared state, your code becomes shockingly correct.
Node.js is single-threaded — until it isn't. Worker Threads let you run CPU-heavy code in parallel without spinning up new processes. Here's how to use them correctly.
Your Laravel app is running tasks sequentially like it's waiting in a McDonald's queue. Laravel 11's Concurrency facade lets you run them all at once. Here's how.
Coming from PHP where you can mutate literally anything from anywhere at any time with zero consequences — until production — Rust's ownership rules feel like a padlock. Interior mutability is the key. The *legal* key.
Coming from 7 years of Laravel/Node.js where 'threading' is either a myth or a callback nightmare, Rust channels rewired how I think about concurrency. Spoiler: your threads shouldn't share a brain.
That moment when two requests arrive at the exact same nanosecond and your app freaks out. Let's fix the vulnerability that only shows up in production!
Coming from 7 years of Node.js callback hell and async/await spaghetti, I thought asynchronous programming was inherently painful. Then I discovered Tokio - Rust's async runtime that's actually elegant, performant, and doesn't turn your code into nested madness!
Think handling 10k concurrent connections requires callbacks from hell or threading nightmares? Rust's async runtime says 'hold my beer' and does it with 50MB of RAM.